Current Issue : July - September Volume : 2014 Issue Number : 3 Articles : 4 Articles
This paper presents the roadmap adopted by Synapsis Brazil to implement the process\nareas of CMMI-DEV Maturity Level 5 in small sized evolutionary projects. We also discuss\nthe results of applying statistical process control in more than 20 projects, and the lessons\nlearned in conducting successfully a SCAMPI A assessment of CMMI-DEV Maturity Level 5....
Background: Despite the increasing number of bug analysis tools for exploring bugs\nin software systems, there are no tools supporting the investigation of causality\nrelationships between internal quality metrics and bugs. In this paper, we propose an\nextension of the BugMaps tool called BugMaps-Granger that allows the analysis of\nsource code properties that are more likely to cause bugs. For this purpose, we relied\non the Granger Causality Test to evaluate whether past changes to a given time series\nof source code metrics can be used to forecast changes in a time series of defects. Our\ntool extracts source code versions from version control platforms, calculates source\ncode metrics and defects time series, computes Granger Test results, and provides\ninteractive visualizations for causal analysis of bugs.\nResults: We provide an example of use of BugMaps-Granger involving data from the\nEquinox Framework and Eclipse JDT Core systems collected during three years. For\nthese systems, the tool was able to identify the modules with more bugs, the average\nlifetime and complexity of the bugs, and the source code properties that are more\nlikely to cause bugs.\nConclusions: With the results provided by the tool in hand, a maintainer can perform\nat least two main software quality assurance activities: (a) refactoring the source code\nproperties that Granger-caused bugs and (b) improving unit tests coverage in classes\nwith more bugs....
Maturity models and Information Technology (IT) service management models\nguide the definition and improvement of service management processes. Known\napproaches include ITIL, COBIT, ISO/IEC 20000, CMMI-SVC, and MR-MPS-SV. The\nimplementation of these models results in benefits such as: increased user and\ncustomer satisfaction with IT services; financial savings due to less rework and less\ntime used, and improved resource management and usage; improved decision\nmaking and optimized risk; and better alignment based on the business focus.\nHowever, some organizations find it difficult to use the models. This paper presents\na study in which we identified critical factors for success and failure of the\nimprovement of IT service processes. By doing a systematic mapping study and\nby snowballing, we were able to identify factors such as: project implementation\nstrategy; support, commitment, and involvement; processes; and internal and\nexternal resources. Also, we analyzed our results using grounded theory procedures\nin order to facilitate their understanding....
Background: Usability is one of the most important factors that determine the\nquality of Web applications, which can be verified performing usability inspection.\nThis paper presents the Web Design Usability Evaluation (Web DUE) technique,\nwhich allows the identification of usability problems in low-fidelity prototypes\n(or mockups) of Web applications during the design phases of the development. We\nhave also proposed the Mockup Design Usability Evaluation (Mockup DUE) tool\nwhich is able to assist inspectors using the Web DUE technique.\nMethod: In order to verify the feasibility of these technologies, we have performed\ntwo empirical studies. During the first study, we compared the effectiveness and\nefficiency indicators of the Web DUE technique with the ones of its predecessor, the\nWeb Design Perspective (WDP) based usability inspection technique. Also, during the\nsecond study, experienced inspectors used the Mockup DUE tool and answered a\nquestionnaire aiming at identifying improvement opportunities in its design.\nResults: The analysis of the quantitative data showed that the Web DUE technique\nallowed the identification of more usability problems in lesser time when compared\nto the WDP technique. Moreover, the qualitative data from the second empirical\nstudy provided information on the tool�s perceived ease of use, indicating that\ninspectors were satisfied and that they would use it to perform a usability inspection\nwith the Web DUE technique.\nConclusions: These results showed that the DUE technologies could be applied in\nthe identification of usability problems early in the design of Web applications. Thus,\ntheir use could enable the correction of such problems before the source code of\nthe application is written....
Loading....